[Logo]

Professional Experience

Main Page
Consulting
Software
Hosting

contact us
Resume
front page
Work history
Other Experience
Education

Computer Languages
Operating Systems
Applications
Hardware

MAP Network Engineering

(1997-present)

Working as an independent Internet Engineering Consultant I have contributed to a wide range of projects. My primary role has been in routing and infrastructure, designing BGP peering and global routing strategies as well as internal network architecture. I have also contributed to product design work for internet integration, and software customization use in specialized or experimental setups.

Clients have included large companies with world wide networks, small ISPs needing highly reliable BGP peering, service providers wanting transparent failover, application developers needing a design for wide scale deployment, and many others.

Projects included a large multinational corporation which had me do an independent evaluation of their existing global internet, with thousands of Ethernets worldwide. This resulted in a validation of the internal architecture, but a complete redesign of the interconnect with the external Internet, including separate DMZ and access Ethernets. Another substantial project was developing a Network Monitoring and Analysis System for Sandstorm Enterprises called NetIntercept. Sandstorm was acquired by NIKSUN largely on the strength of this product.

BBN

[formerly Bolt Beranek and Newman]
(1992 to 1996)

1996: Working in the Network Engineering Department I did several Engineering tasks for the nationwide BBN PlaNet network. These included both working with clients of the network to solve complex problems escalated from the front-line operations staff and also long term performance analysis for customers in the marketing department in support of new product offerings.

From 1995 through 1996: As a member of the Research Staff in the Advanced Network Technology Department, I did software development and operational analysis on several leading edge network experiments. These included developing visualization tools for a new Internet Routing Architecture (Nimrod) and performance analysis of a test of a new multicast forwarding paradigm.

From 1992 through 1995: As Network Engineer in the Real-Time Networking Department, I had primary engineering responsibility for operation of a worldwide network for the DoD. Primary duties included designing and implementing peering policies with other large networks, simplifying and then documenting the internal routing structure, configuring and tuning of routers, consulting on operational and QA/deployment activities. Additionally I did development of a web site for the network, and some programming of tools for network monitoring--including automated network map generation--and configuration management. I attended IETF to keep abreast of trends in The Internet and NANOG (formerly NSFnet Regional Techs) to coordinate with other network operators.

MIT Laboratory for Computer Science

(1987 to 1992)

As Network Manager for LCS I oversaw a network of nearly 400 hosts including a few small personal computers, large numbers of workstations, and some large timesharing service machines. The network used principally the TCP/IP and Chaos protocol suites. My responsibilities included planning, operations, and development. I was responsible for recognizing areas of future expansion and designing network solutions based on user requirements and integrate these with the Lab-wide plan. I was also responsible for maintaining the software running on most of the Lab's gateways (a locally developed system called CGW), as well as configuration of all the gateways and the overall network. I monitored day-to-day activity on the network and watched for problems while they were still in developmental stages. I worked with several different facilities for monitoring, including a set of tools I developed specifically around LCS's unique requirements. This included a complete multi-protocol Network Management System for TCP/IP and Chaos networks using ICMP, SNMP, and other protocols. Additional responsibilities included representation at various organizations including IETF and DECUS.

Perception Technology

(1982 to 1987)

I started as Chief Systems Programmer and became Manager of Software Development in 1985. My major project at Perception was the development and support of a Real-time data communications system which runs on LSI-11 processors. This system was the company's Vocom-I series product for which I was still the primary support person when I left. These positions included responsibility for answering user questions and assisting in correcting problems on the Company's time sharing systems. I also acted as the primary contact for persons in the Hardware and Manufacturing departments for questions concerning analysis of system failures. I also acted as an adviser to members of the Software Development Department in the design and coding of their individual projects. I was also responsible for implementing tools to aid the members of the department in developing new systems. These included maintaining a C compiler and its run-time library for three operating systems, a listing maintenance package, a system build program (similar to UNIX `make'), an EMACS-like editor written in C, a serial line file transfer program, and the previously mentioned Vocom-I system. I was also involved in planning for new products, including personnel availability, cost/benefit analysis of proposed systems, and development and maintenance time projections.

MIT Laboratory for Computer Science

(1981 to 1982)

While completing my degree I worked part-time as a Programmer in the Computer Systems Communications group at LCS. During this time I worked on many projects in networking and systems. I also assisted in hardware and software maintenance on a UNIX V6 system running on PDP-11 series computers.

Brigham and Women's Hospital

(1979 to 1981)

I worked as Assistant System Manager on the Radiology Department's computer systems which included a PDP-11/70 running RSX11-D and a VAX 11/780 running VMS. My primary responsibilities were in the communications area. I was responsible for connecting and rearranging all terminal connections to both machines. I was also responsible for recommending purchases for the data communications needs of the user community on these machines which included many local and remote users with a variety of connection requirements. I also helped develop many software tools used for control of the system and for developing application software.

Massachusetts Institute of Technology

(1973 to 1978)

While I was a student at the Massachusetts Institute of Technology, I did Programming for various laboratories including:

Artificial Intelligence laboratory: Lisp Machine system programming (in LISP) mostly CHAOSnet network software.
Psychology Dept: Low level subroutines for interface to graphic hardware.
Center for Space Research: Data analysis applications in Fortran with some Assembly language for speed.
Center for Materials Science and Engineering: Interpreter for an intermediate language for graphic data.
Dormitory Telephone Services: Technician for installation of Central Office (CO) equipment.
Architecture Machine Group: (now the Media Lab) Graphics device drivers and display processor code.

Outlet Company

(1970 to 1976)

Accounting software on NCR Century and IBM 360 mainframes.



Web site designed, developed and hosted by MAP Network Engineering
MAP Network Engineering uses, supports and recommends Open Source software and open standards.
[Powered by NetBSD] Powered by Roxen [Powered by MySQL] [Open Source Iniative] [Self professed Hacker] [Best viewed with ANY browser] [Valid HTML 4.01!]
Use of the logos above does not imply endorsement by the respective organizations of MAP Network Engineering sites or services.
On the contrary it implies endorsement by MAP Network Engineering of those organizations or software.


Page generated 2024-11-25 at 17:37 GMT
Copyright © MMXXIV MAP Network Engineering


And finally, a random note:
If you are not part of the solution, then you are part of the precipitate.